fix(entry-skills): every handoff arm says to invoke the skill#552
Merged
Conversation
This was referenced Jul 26, 2026
Merged
This was referenced Jul 27, 2026
leeovery
force-pushed
the
docs/contributing
branch
from
July 27, 2026 14:32
52f416f to
bf2c67f
Compare
leeovery
force-pushed
the
fix/spec-entry-bugfix-invoke
branch
from
July 27, 2026 14:32
d7c7000 to
463421f
Compare
leeovery
force-pushed
the
docs/contributing
branch
from
July 27, 2026 14:34
bf2c67f to
f051286
Compare
leeovery
force-pushed
the
fix/spec-entry-bugfix-invoke
branch
from
July 27, 2026 14:34
463421f to
1f0b42d
Compare
leeovery
force-pushed
the
docs/contributing
branch
from
July 27, 2026 14:37
f051286 to
3b02bab
Compare
leeovery
force-pushed
the
fix/spec-entry-bugfix-invoke
branch
from
July 27, 2026 14:37
1f0b42d to
9cb8ef4
Compare
leeovery
force-pushed
the
docs/contributing
branch
from
July 27, 2026 14:39
3b02bab to
c4da5c4
Compare
leeovery
force-pushed
the
fix/spec-entry-bugfix-invoke
branch
from
July 27, 2026 14:39
9cb8ef4 to
30714f1
Compare
leeovery
force-pushed
the
docs/contributing
branch
from
July 27, 2026 14:41
c4da5c4 to
78dc5f1
Compare
leeovery
force-pushed
the
fix/spec-entry-bugfix-invoke
branch
from
July 27, 2026 14:41
30714f1 to
4324479
Compare
leeovery
force-pushed
the
docs/contributing
branch
from
July 27, 2026 14:43
78dc5f1 to
7c1dd40
Compare
leeovery
force-pushed
the
fix/spec-entry-bugfix-invoke
branch
from
July 27, 2026 14:43
4324479 to
74dccf4
Compare
Found by a prose-test walker on the bugfix path: the arm hands over a fenced block of arguments and never says what to do with it — no invocation directive, and no directive to emit it either. Reproduced on both independent walks against the already-fixed fences, so it is not a rendering artefact. Enumerating before fixing turned one arm into four, across three files: specification-entry's `bugfix` and `cross-cutting`, investigation-entry's `continue`, and planning-entry's `continuing or reviewing`. In each case a sibling arm in the same file carries the sentence and these do not. discussion-entry and research-entry carry it on every arm, which is what shows this is an omission rather than a house style — the same proof that settled the fences. Additions only; the fences were re-verified intact afterwards. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
leeovery
force-pushed
the
fix/spec-entry-bugfix-invoke
branch
from
July 27, 2026 14:45
74dccf4 to
2bc520f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
DEVIATION: the arm hands over a fenced block of arguments and never says what to do with it — no invocation directive, and no directive to emit it either. Reproduced identically on both independent walks, against the already-fixed fences, so it isn't a rendering artefact.workflow-specification-entry#### If work_type is bugfixworkflow-specification-entry#### If work_type is cross-cuttingworkflow-investigation-entry#### If source is continueworkflow-planning-entry#### If continuing or reviewing existing plandiscussion-entryandresearch-entrycarry it on every arm — the same proof structure that settled the fence bug: two files doing it correctly means the others are omissions, not house style.Test plan
npm testgreen: 1699 tests, 0 fail.🤖 Generated with Claude Code
Stack